Method, apparatus, and mobile terminal for associating notification messages

ABSTRACT

A method, an apparatus, and a mobile terminal for associating notification messages that relate to the field of information technologies, where the method includes obtaining semantic feature values of notification messages in different applications, and associating notification messages in different applications and whose semantic feature values match such that associate notification messages of associated events of a mobile terminal from different channels, thereby resolving a problem that notification messages of associated events are dispersedly distributed and are prone to be forgotten by a user. Therefore, the user can conveniently view notification messages of associated events from different channels, thereby effectively improving operation efficiency of the user, and improving user experience.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a U.S. National Stage of International PatentApplication No. PCT/CN2016/098581 file on Sep. 9, 2016, which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

The present invention relates to the field of information technologies,and in particular, to a method, an apparatus, and a mobile terminal forassociating notification messages.

BACKGROUND

With continuous development of smart electronic devices and mobileterminals, a user is increasingly accustomed to obtaining variousnotification messages by using a mobile phone. A notification messagerelated to express delivery tracking is used as an example. FIG. 1 is aschematic diagram of an interface in which a mobile phone presentsexpress delivery tracking information in the prior art. A user usuallyopens an application (for example, a Taobao application) or logs on to aweb page (for example, Taobao.com), to query a tracking status from aserver by using a tracking number, and then the mobile phone presentsexpress delivery information shown in FIG. 1. The express deliveryinformation includes collection information, transit information,signing information, and the like. Because the express deliveryinformation in the server is entered by a courier after delivering apackage, and therefore is delayed. In addition, during package delivery,the courier usually notifies, in a form of an SMS message or a call, auser of when and where to pick up the package. Therefore, the user needsto perform a plurality of operations to obtain complete express deliverytracking information. To be specific, the user first needs to view theinterface shown in FIG. 1 to acknowledge shipment information and atransit status. Then the user needs to view an address book or an SMSmessage to acknowledge delivery information of the courier. If the userdoes not sign for the package face-to-face, the user further needs toopen an SMS application to view an intelligent self-express servicemachine and a password. Consequently, operation efficiency is relativelylow, and user experience is low.

SUMMARY

The present invention provides a method and a mobile terminal forassociating notification messages, to resolve a prior-art technicalproblem that information of a same event is dispersedly distributed, anda user opens a plurality of applications to perform a plurality ofoperations, causing low operation efficiency and low user experience.

According to a first aspect, this solution provides an embodiment of amethod for associating notification messages.

In a first possible implementation, the method includes: obtaining afirst notification message in a first application; obtaining a semanticfeature value of the first notification message, where the semanticfeature value is used to indicate a semantic feature of the firstnotification message; determining a second notification message in asecond application, wherein a semantic feature value of the secondnotification message matches the semantic feature value of the firstnotification message, where the second notification message ispre-stored in the mobile terminal; and associating the firstnotification message with the second notification message. In thismethod, notification messages that are of associated events of themobile terminal and that are from different channels (for example,different applications) are associated, thereby resolving a prior-artproblem that notification messages of associated events are dispersedlydistributed and prone to be forgotten by a user. Therefore, the user canconveniently view notification messages that are of associated eventsand that are from different channels, thereby effectively improvingoperation efficiency of the user, and improving user experience.

With reference to the first possible implementation of the first aspect,in a second possible implementation, the determining, by a mobileterminal, that a semantic feature value of a second notification messagematches the semantic feature value of the first notification message maybe: determining that an event related to the second notification messageand an event related to the first notification message are a same event.Notification messages of a same event that are from differentapplications are associated in this solution, so that the user canquickly view the notification messages. If different notificationmessages indicate different states of a same event, for example, thefirst notification message indicates that the event is in a first state,and the second notification message indicates that the event is in asecond state, the mobile terminal may separately store the first stateand the second state, and update a current status of the event to alatest state, so as to help the user learn of current progress of theevent and the latest state of the event. Further, if the updated lateststate is an important state in a life cycle of the event, for example, adelivery state in an express delivery event, after updating the statusof the event, the mobile terminal may further prompt the user with thecurrent status of the event, so as to prevent the user from omitting arelated notification message.

With reference to the first possible implementation of the first aspect,in a third possible implementation, the determining, by a mobileterminal, that a semantic feature value of a second notification messagematches the semantic feature value of the first notification message maybe: obtaining the semantic feature value of the second notificationmessage; and determining that the semantic feature value of the secondnotification message is the same as or similar to the semantic featurevalue of the first notification message. When the semantic featurevalues are the same, content to which one of the two notificationmessages points is consistent with content to which the othernotification message points. When the semantic feature values aresimilar to each other, the two notification messages may be stronglyrelated to each other. The two cases ensure that the mobile terminal canassociate notification messages of associated events, thereby helpingthe user classify and view the notification messages.

With reference to the first, the second, or the third possibleimplementation of the first aspect, in a fourth possible implementation,the mobile terminal may associate the first notification message withthe second notification message in a plurality of forms. For example,the mobile terminal sequentially presents the first notification messageand the second notification message in a same interface based on aprogress sequence of the same event; or the mobile terminal sequentiallypresents the first notification message and the second notificationmessage in a same interface based on a time sequence of receiving thenotification messages; or the mobile terminal presents the firstnotification message and the second notification message in a sameinterface, and the presentation may not be displayed based on thesequence mentioned above; or the mobile terminal sequentially broadcaststhe first notification message and the second notification messagethrough a voice based on a time sequence. Through a variety ofassociation forms, it is convenient for the user to view thenotification message clearly and simply, to learn of progress of theevent and content of the notification message in a timely manner.

Further, the interface presenting the first notification message and thesecond notification message is an interface in the first application, ormay be an interface in the second application, or may be an interfaceregenerated by the mobile terminal. Specific display may be determinedby the mobile terminal based on an actual situation. For example, theterminal may present the notification messages in the interface in thefirst application according to a most concise and effective standard, ormay present the notification messages in the regenerated interfaceaccording to a standard that all notification message content ispresented.

With reference to the fourth possible implementation of the firstaspect, in a fifth possible implementation, a first interface element isconfigured in the interface presenting the first notification messageand the second notification message. The mobile terminal may furtherobtain an instruction for triggering the first interface element by theuser, and invoke a third application. A semantic feature value of thethird application matches the semantic feature value of the firstnotification message, or a semantic feature value of the thirdapplication matches the semantic feature value of the secondnotification message. The interface element may be an icon or the like.By taping the icon, the user may directly invoke an associatedapplication to perform a corresponding function, so as to save the userfrom performing a plurality of operations such as exiting a currentinterface, selecting an application from a home interface, and enteringan execution function, thereby effectively improving applicationoperation efficiency.

With reference to any one of the first to the fifth possibleimplementations of the first aspect, in a sixth possible implementation,the first notification message carries a first time point andinformation about an action to occur at the first time point, and thefirst time point is a future time point. The mobile terminal may furtherobtain the first time point carried in the first notification message,and automatically generate a schedule reminder based on the first timepoint and the information about the action to occur at the first timepoint. The schedule reminder is used to remind, before the first timepoint, the user of the action to occur at the first time point. Themobile terminal may automatically generate a reminder item by obtaininga time and an event in a notification message, to remind the user not tomiss the time. Therefore, the mobile terminal is more intelligent,thereby helping the user make a time plan in advance.

With reference to any one of the first to the sixth possibleimplementations of the first aspect, in a seventh possibleimplementation, the first notification message carries a first locationand information about an action to occur at the first location. Themobile terminal may further obtain a current location of the mobileterminal, and automatically generate a reminder item if deviationbetween the current location of the mobile terminal and the firstlocation falls within a preset deviation range. The reminder item isused to prompt for the information about the action to occur at thefirst location. By obtaining a location and an event in a notificationmessage, the mobile terminal may obtain a current location in a realtime, and automatically generate a reminder item, to remind the user ofan event related to the current location. Therefore, the mobile terminalis more intelligent, thereby helping the user arrange an itinerary ofthe user.

According to a second aspect, this solution provides an embodiment of amobile terminal for associating notification messages. The mobileterminal may be configured to perform any possible implementationmentioned in the first aspect, and a structure of the mobile terminal isdescribed in a specific embodiment.

According to a third aspect, this solution provides an embodiment of anapparatus for associating notification messages. The apparatus may beconfigured to perform any possible implementation mentioned in the firstaspect, and a structure of the apparatus is described in a specificembodiment.

According to a fourth aspect, this solution provides an embodiment of acomputer storage medium for associating notification messages, and thestorage medium may be configured to perform any possible implementationmentioned in the first aspect.

In the method, semantic feature values of notification messages indifferent applications are obtained, and notification messages that arein different applications and whose semantic feature values match areassociated, so as to associate notification messages that are ofassociated events of a mobile terminal and that are from differentchannels (for example, different applications), thereby resolving aprior-art problem that notification messages of associated events aredispersedly distributed and are prone to be forgotten by a user.Therefore, the user can conveniently view notification messages that areof associated events and that are from different channels, therebyeffectively improving operation efficiency of the user, and improvinguser experience.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentinvention more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments or theprior art. Apparently, the accompanying drawings in the followingdescription show merely some embodiments of the present invention, andpersons of ordinary skill in the art may derive other drawings fromthese accompanying drawings without creative efforts.

FIG. 1 is a schematic diagram of an interface in which a mobile phonepresents express delivery tracking information in the prior art;

FIG. 2 is a schematic diagram of a notification message conceptaccording to an embodiment of the present invention:

FIG. 3 is a schematic structural diagram of a mobile terminal forassociating notification messages according to an embodiment of thepresent invention;

FIG. 4 is a schematic structural diagram of a mobile terminal forassociating notification messages according to an embodiment of thepresent invention:

FIG. 5 is a schematic flowchart of a method for associating notificationmessages according to an embodiment of the present invention;

FIG. 6A to FIG. 6C are a schematic flowchart of a method for associatingnotification messages according to an embodiment of the presentinvention;

FIG. 7 is a schematic flowchart of a method for associating notificationmessages according to an embodiment of the present invention:

FIG. 8 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention:

FIG. 16 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 17 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 18 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 20 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 21 is a schematic diagram of a notification message presentationinterface according to an embodiment of the present invention;

FIG. 22 is a schematic structural diagram of a mobile terminal forassociating notification messages according to an embodiment of thepresent invention; and

FIG. 23 is a schematic structural diagram of an apparatus forassociating notification messages according to an embodiment of thepresent invention.

DESCRIPTION OF EMBODIMENTS

To make the objectives, technical solutions, and advantages of thepresent invention clearer, the following further describes theimplementations of the present invention in detail with reference to theaccompanying drawings. All other embodiments obtained by persons ofordinary skill in the art without creative efforts shall fall within theprotection scope of the present invention. In specific descriptions ofthe following embodiments, related concepts are further explained basedon technical understanding of persons of ordinary skill in the art. Itshould be noted that these concepts constitute no limitation onexplanations of a concept and a term well known in the technical field.

A mobile terminal, which may also be referred to as user equipment (UserEquipment, UE) or an intelligent terminal, includes but is not limitedto a mobile phone, a mobile computer, a tablet computer, a personaldigital assistant (Personal Digital Assistant, PDA), a media player, asmart television, a smartwatch, smart glasses, a smart band, and thelike. A method for updating a notification message in the presentinvention may be applied to various mobile terminals. A specificimplementation is described below by using a mobile terminal performingthe method as an example. In other implementations of the presentinvention, a well-known method, process, component, and circuit are notdescribed in detail.

An operating system (Operating System, OS) is a computer program thatmanages computer hardware and software resources, and is a kernel and acornerstone of a computer system. Development of mobile communicationstechnologies brings rapid development of mobile terminal technologies.An operating system running on a terminal device may be a Linuxkernel-based operating system such as Android of a mobile version,Ubuntu of a mobile version, or Tizen, a Windows phone system and an iOSsystem, and a BlackBerry system or a Symbian system, and furtherincludes but is not limited to a desktop operating system such asWindows, a Mac OS, or Linux. Android is used as an example. As aplatform of a mobile device. Android has a software hierarchicalstructure including an operating system (OS), a middleware (MiddleWare),and an application (Application). The software hierarchical structure ofAndroid is divided into the following layers from bottom to top: first,an operating system (OS) layer; second, various libraries (Libraries)and Android runtime (RunTime); third, an application framework(Application Framework); and fourth, an application (Application).Specific content at the layers is not described in detail.

A semantic feature may be understood as follows: A semantic class issub-classified from a specific point of view, so that words belonging toa same semantic class may have different values in terms of a semanticfeature or some semantic features, thereby highlighting a differencebetween these words. The values of the semantic feature or the semanticfeatures are semantic feature values, and the semantic feature value isused to indicate a semantic feature of an application, a notificationmessage, or a field. For example, if an application is “Jingdong” or“Taobao”, after performing semantic analysis on the application, amobile terminal may determine that a semantic feature value of theapplication is “shopping”, “e-commerce”, or the like. If an applicationis “Baidu Maps”, the mobile terminal may determine that a semanticfeature value of the application is “map”, “city”, “scenic spot”, or thelike. In this solution, the semantic feature value may include at leastone of the following types: a type of an event related to a notificationmessage, a status of the event related to the notification message, atime of the event related to the notification message, a location of theevent related to the notification message, an order number of the eventrelated to the notification message, a person participating in the eventrelated to the notification message, a time when the mobile terminalreceives the notification message, a sender of the notification message,and the like. For example, the mobile terminal may determine anotification message shown in FIG. 1 as express delivery typeinformation, and may perform semantic analysis on a field in thenotification message to obtain semantic feature values such as an eventtype, event status information, and time information of the notificationmessage. For example, it is identified that the event type of thenotification message is express delivery, event states related to thenotification message are sequentially “collected”, “being transported”,“being delivered”, “signed”, and the like, time points related to thenotification message are respectively time points related to the states,and an express delivery number related to the notification message is32045687464564, and so on.

In the embodiments of the present invention, a notification message maybe understood as a notification type message sent by an object toanother object, as shown in FIG. 2. The object may be a server, or maybe a mobile terminal. The notification message may be a data messageexchanged between the server and the mobile terminal, or may be a datamessage exchanged between mobile terminals. After the notificationmessage is analyzed, an event type, a sending object, an event status,and the like that are related to the notification message may bedetermined. The notification message is carried in various forms. Themobile terminal may present the notification message to a user by usinga UI (User Interface, graphical user interface), or may play thenotification message to a user through a sound. For example, thenotification message may be an SMS message carried in a text form in anSMS application, or a multimedia message carried in a picture form; maybe a message presented in a shopping type application (for example,Taobao) in a manner similar to that in FIG. 1; or may be content carriedin a voice form in a call or a voice chat, for example, a voice chat ina phone call made to a friend or in a chat made with a friend throughWeChat. Examples of the notification message are as follows: a shoppingtype notification message generated when a user shops online and anexpress delivery type notification message generated accordingly, wherecontent of the shopping type notification message may include at leastan order number, a purchased article, a purchase date, and the like, andcontent of the express delivery type notification message may include atleast an express delivery number, an express delivery status, a timepoint of each state, and the like; a flight type notification messagegenerated when a user books a flight ticket, where content of the flighttype notification message may include at least a flight number, a flighttime, a departure airport, and a landing airport; a movie typenotification message generated when a user books a movie ticket, wherecontent of the movie type notification message may include at least amovie name, a play time, a theater name, and the like; and a bank typenotification message generated when a user handles a bank service, wherecontent of the bank type notification message may include at least ahandling time, a handling item, a handling location, and the like. Withreference to understanding of persons of ordinary skill in the art, thenotification message may be received and displayed in a systemnotification bar, and the user is reminded of the notification messagethrough a ring or vibration; or the notification message may be obtainedby an application inside the mobile terminal, and the user is notreminded of the notification message.

The notification message includes a plurality types of content, andrelated key information may be referred to as key content. The keycontent may be defined as an object and content that need to be clear toimplement a function or to do something, for example, a type, a time, alocation, a destination, a status, and an order number that are of thenotification message. Each object field or content field that identifiesthe key content may be referred to as a key field. The key field is invarious forms, and may be any voice content, any text content, or aspecific format field. The type of the notification message is used torepresent a type of the notification message, for example, whether thetype of the notification message is an express delivery type, a flighttype, a bank type, an e-commerce type, or the like. The time is a timerelated to the notification message, such as a sending time or areceiving time of the notification message, or an occurrence time of anevent related to the notification message. The location is a locationrelated to the notification message, such as an occurrence location ofthe event related to the notification message or a destination of theevent. The status is used to represent progress of the event related tothe notification message, such as package collected or signed or aflight delay. A more detailed key field indicates high accuracy, andmore captured content indicates higher accuracy and better practicality.It should be noted that in the embodiments of the present invention, thekey field and the semantic feature value describe same content fromdifferent perspectives, and the key field and the semantic feature valueare essentially consistent with each other. In some scenarios, a valueof the key field is consistent with a value of the semantic featurevalue, and the key field is equal to the semantic feature value.

In the prior art, a mobile terminal usually obtains a notificationmessage from a plurality of channels. Even for a plurality ofnotification messages of a same handling transaction, the mobileterminal cannot effectively merge the notification messages from theplurality of channels because the notification messages are expresseddifferently, are in various forms, and are distributed in a plurality ofapplications. Consequently, it is difficult for a user to associate theplurality of notification messages with a specific transaction. As aresult, the user needs to perform a plurality of operations to learn ofentire information, and operation efficiency is relatively low. For thisproblem, the present invention provides an embodiment of a mobileterminal, and a schematic structural diagram of the mobile terminal isshown in FIG. 3. It should be understood that a mobile terminal 300shown in the figure is only an example, and an actual product may havemore or fewer parts than those shown in FIG. 3, may combine two or moreparts, or may have different part configurations. The mobile terminalshown in the figure may be configured to perform a method shown in FIG.5. FIG. 6A to FIG. 6C, or FIG. 7. Various parts shown in FIG. 3 may beimplemented in hardware that includes one or more signal processingand/or application-specific integrated circuits, in software, or in acombination of hardware and software. As shown in the figure, the mobileterminal 300 includes parts such as an RF (Radio Frequency, radiofrequency) circuit 310, a memory 320, an input unit 330, a display unit340, a sensor 350, an audio frequency circuit 360, a Wi-Fi (WirelessFidelity, Wireless Fidelity) module 370, a processor 380, and a powersupply 390. The composition parts are described below in detail.

The RF circuit 310 may be configured to receive and send a signal in aninformation receiving and sending process or a call process. Inparticular, after receiving downlink information from a base station,the RF circuit 310 sends the downlink information to the processor 380for processing, and sends related uplink data to the base station. TheRF circuit usually includes but is not limited to an antenna, at leastone amplifier, a transceiver, a coupler, an LNA (Low Noise Amplifier,low noise amplifier), a duplexer, and the like. In addition, the RFcircuit 310 may further communicate with a network and another devicethrough wireless communication. Any communications standard or protocolmay be used for the wireless communication, and the communicationsstandard or protocol includes but is not limited to a GSM (Global Systemof Mobile communication, Global System for Mobile Communications), GPRS(General Packet Radio Service, general packet radio service), CDMA (CodeDivision Multiple Access, Code Division Multiple Access), WCDMA(Wideband Code Division Multiple Access, Wideband Code Division MultipleAccess), LTE (Long Term Evolution, Long Term Evolution), an email, anSMS (Short Messaging Service, short message service), and the like.

The memory 320 may be configured to store a software program and amodule, and the processor 380 runs the software program and the modulestored in the memory 320 to perform various function applications of themobile terminal 300 and data processing. The memory 320 may mainlyinclude a program storage area and a data storage area. The programstorage area may store an operating system, an application required byat least one function (for example, a sound playing function and animage playing function), and the like. The data storage area may storedata (for example, audio data and a phone book) created based on use ofthe mobile terminal 300, and the like. In addition, the memory 320 mayinclude a high-speed random access memory, and may further include anonvolatile memory, for example, at least one magnetic disk storagedevice, a flash storage device, or another volatile solid-state storagedevice.

The input unit 330 may be configured to: receive digit or characterinformation that is input, and generate key signal input related to usersetting and function control of the mobile terminal 300. Specifically,the input unit 330 may include a touch panel 331 and another inputdevice 132. The touch panel 331, also referred to as a touchscreen, maycollect a touch operation performed by a user on or near the touch panel(for example, an operation performed by the user on or near the touchpanel 331 by using any suitable object or accessory such as a finger ora stylus), and may drive a corresponding connection apparatus accordingto a preset program. Optionally, the touch panel 331 may include twoparts: a touch detection apparatus and a touch controller. The touchdetection apparatus detects a touch location of the user, detects asignal brought by the touch operation, and transmits the signal to thetouch controller. The touch controller receives touch information fromthe touch detection apparatus, converts the touch information into touchpoint coordinates and then sends the touch point coordinates to theprocessor 380, and can receive and execute a command sent by theprocessor 380. In addition, the touch panel 331 may be implemented byusing a plurality of types such as a resistive type, a capacitive type,an infrared ray, and a surface acoustic wave. In addition to the touchpanel 331, the input unit 330 may include the another input device 132.Specifically, the another input device 132 may include but is notlimited to one or more of a physical keyboard, a function key (such as avolume control key or an on/off key), a trackball, a mouse, a joystick,and the like.

The display unit 340 may be configured to display information entered bythe user or information provided for the user, and various menus of themobile terminal 300. The display unit 340 may include a display panel341. Optionally, the display panel 341 may be configured in a form of anLCD (Liquid Crystal Display, liquid crystal display), an OLED (OrganicLight-Emitting Diode, organic light-emitting diode), or the like.Further, the touch panel 331 may cover the display panel 341. Whendetecting the touch operation on or near the touch panel 331, the touchpanel 331 transmits the touch operation to the processor 380 todetermine a type of a touch event, and then the processor 380 providescorresponding visual output on the display panel 341 based on the typeof the touch event. In FIG. 3, the touch panel 331 and the display panel341 serve as two independent components to implement input and outputfunctions of the mobile terminal 300. However, in some embodiments, thetouch panel 331 and the display panel 341 may be integrated to implementthe input and output functions of the mobile terminal 300.

The mobile terminal 300 may further include at least one sensor 350,such as a fingerprint sensor, a light sensor, a motion sensor, andanother sensor. Specifically, the fingerprint sensor is configured toidentify fingerprint information entered by the user. The light sensormay include an ambient light sensor and a proximity sensor. The ambientlight sensor may adjust brightness of the display panel 341 based onluminance of ambient light, and the proximity sensor may disable thedisplay panel 341 and/or backlight when the mobile terminal 300approaches an ear. As a motion sensor, an accelerometer sensor maydetect a value of acceleration in each direction (usually three axes),may detect a value and a direction of gravity in a static state, and maybe configured to identify an application of a mobile terminal posture(such as switching between a landscape mode and a portrait mode, arelated game, and magnetometer posture calibration), a function relatedto vibration identification (such as a pedometer and a knock), and thelike. Other sensors such as a gyroscope, a barometer, a hygrometer, athermometer, and an infrared sensor may be further configured in themobile terminal 300, and details are not described herein.

The audio frequency circuit 360, a loudspeaker 361, and a microphone 362may provide an audio interface between the user and the mobile terminal300. The audio frequency circuit 360 may convert received audio datainto an electrical signal and then transmit the electrical signal to theloudspeaker 361, and the loudspeaker 361 converts the electrical signalinto a sound signal for output. In addition, the microphone 362 convertsthe collected sound signal into an electrical signal, and the audiofrequency circuit 360 receives the electrical signal, converts theelectrical signal into audio data, and then outputs the audio data tothe RF circuit 108, so as to send the audio data to, for example,another mobile terminal, or output the audio data to the memory 320 forfurther processing.

Wi-Fi belongs to a short-range wireless transmission technology. Themobile terminal 300 may help, by using the Wi-Fi module 370, the userreceive and send an email, browse a web page, access streaming media,and so on. The Wi-Fi module 370 provides the user with wirelessbroadband Internet access. Although FIG. 3 shows the Wi-Fi module 370,it may be understood that the Wi-Fi module 370 is not a mandatorycomponent of the mobile terminal 300, and may be omitted according to arequirement without changing the essence of the present invention.

As a control center of the mobile terminal 300, the processor 380 isconnected to each part of the entire mobile terminal by using variousinterfaces and cables, and runs or executes the software program and/orthe module stored in the memory 320 and invokes data stored in thememory 320, to perform various functions of the mobile terminal 300 anddata processing, so as to perform overall monitoring on the mobileterminal. Optionally, the processor 380 may include one or moreprocessing units. Preferably, an application processor and a modemprocessor may be integrated into the processor 380. The applicationprocessor mainly processes an operating system, a user interface, anapplication, and the like. The modem processor mainly processes wirelesscommunication. It may be understood that the modem processor mayalternatively not be integrated into the processor 380.

The mobile terminal 300 further includes the power supply 390 (forexample, a battery) that supplies power to each part. Preferably, thepower supply may be logically connected to the processor 380 by using apower management system, so as to implement functions such as chargingmanagement, discharging management, and power consumption management byusing the power management system.

Although not shown in the figure, the mobile terminal 300 may furtherinclude a camera, a Bluetooth module, and the like. Details are notdescribed herein.

As shown in FIG. 4, the operating system stored in the memory 320 mayinclude an application 410, a content capturing module 420, a semanticanalysis module 430, and a notification message management module 440.The application 410 is a set of applications related to dailyapplication of a mobile phone, for example, a set of applications suchas an SMS message, a phone, WeChat, and Taobao. The content capturingmodule 420 may capture content of a notification message related to anapplication in the application 410, for example, capture informationsuch as an SMS message, a WeChat notification, words on a Taobao page,and a recording in a phone call or WeChat. After capturing the contentof the notification message, the content capturing module 420 may sendthe message content to the semantic analysis module 430. The semanticanalysis module 430 performs semantic analysis on the content of thenotification message to extract key content of the notification message,and sends the key content to the notification message management module440. After obtaining the key content, the notification messagemanagement module 440 searches for a locally stored notification messagebased on the key field. If a notification message matching the key fieldis stored, the notification message management module 440 updatesdecoration of the stored notification message; or if there is nonotification message matching the key field, the notification messagemanagement module 440 creates a record, stores the content of thenotification message, and refreshes the content of the notificationmessage after receiving a related notification message. Persons ofordinary skill in the art may understand that the content capturingmodule 420, the semantic analysis module 430, and the notificationmessage management module 440 may be software modules stored in thememory. From a perspective of hardware implementation, the processor 380may invoke module code in the memory 320 to implement the solution ofthe present invention.

FIG. 5 is a schematic flowchart of a method for associating notificationmessages according to an embodiment of the present invention, and themethod includes the following steps.

S501. A mobile terminal obtains a first notification message in a firstapplication.

That a mobile terminal obtains a first notification message in a firstapplication may be as follows: After obtaining the first notificationmessage, the mobile terminal sends the first notification message to thefirst application for processing; or the mobile terminal may receive thefirst notification message by using the first application. For example,the mobile terminal obtains an SMS message in an SMS application, WeChatinformation in a WeChat application, an express delivery typenotification message in a Taobao application, a notification message ina bank type application, a notification message in a shopping typeapplication, and the like.

S502. The mobile terminal obtains a semantic feature value of the firstnotification message, where the semantic feature value is used toindicate a semantic feature of the first notification message.

The mobile terminal performs semantic analysis on the first notificationmessage after obtaining the first notification message. A semanticanalysis technology is relatively mature, and is a powerful technologyused to obtain and understand text information by analyzing informationexchanged between nodes in a social network. The semantic feature valueof the first notification message may be obtained based on analysis ofthe first notification message.

S503. The mobile terminal determines a second notification message in asecond application, wherein a semantic feature value of the secondnotification message matches the semantic feature value of the firstnotification message, where the second notification message ispre-stored in the mobile terminal.

After obtaining the semantic feature value of the first notificationmessage, the mobile terminal may search for a stored notificationmessage based on the semantic feature value. For example, the mobileterminal maintains a table of semantic feature values of notificationmessages. The mobile terminal looks up the table to obtain the secondnotification message whose semantic feature value matches the semanticfeature value of the first notification message. That a semantic featurevalue of a second notification message matches the semantic featurevalue of the first notification message includes the following: An eventrelated to the second notification message and an event related to thefirst notification message are a same event. For example, an SMS messagein the SMS application and a notification message in an e-commerceapplication are related to a same order number or a same expressdelivery number. Alternatively, the semantic feature value of the secondnotification message is the same as or similar to the semantic featurevalue of the first notification message. For example, the semanticfeature values are related to different attributes of a same location,but the different attributes point to the same location. For example,both a capital of China and a political center of China point toBeijing. Specifically, the mobile terminal may match the semanticfeature value of the first notification message and the semantic featurevalue of the second notification message. A matching standard may bebased on whether the semantic feature values are the same or similar.The former may include at least whether meanings of the notificationmessages are the same, whether the feature values are consistent witheach other, and so on. The latter may include at least whether thenotification messages have a correlation, whether the notificationmessages conform to a context, whether the feature values are synonyms,and so on.

S504. The mobile terminal associates the first notification message withthe second notification message.

Specifically, the association may be understood in a broad sense, thatis, the first notification message and the second notification messagemay be expressed in any form, including various forms for displaying andpresenting the notification messages, such as a visual form, an auditoryform, and a tactile form. Examples may include at least the following:

In a visual presentation scenario, the first notification message andthe second notification message are presented in a same interface; orthe first notification message and the second notification message aresequentially presented in a same interface based on a time sequence ofreceiving the notification messages; or the first notification messageand the second notification message are sequentially presented in a sameinterface based on a progress sequence of the event, for example, asequence of collection, shipment, delivery, and receipt of a package; ora key similar to a hyperlink is disposed at the first notificationmessage, and the second notification message may be directly opened bytaping the key. The interface presenting the first notification messageand the second notification message is an interface in the firstapplication; or the interface presenting the first notification messageand the second notification message is an interface in the secondapplication; or the interface presenting the first notification messageand the second notification message is an interface regenerated by themobile terminal. The regenerated interface may be an interface in athird application, or an interface that is separately generated by themobile terminal and that does not belong to a third-party application.

In an auditory scenario, the first notification message and the secondnotification message may be played in a same context, and this furtherincludes that the first notification message and the second notificationmessage are sequentially played in the same context based on a timesequence.

In a tactile environment, if a mobile phone is related to a tactilepassword, the first notification message and the second notificationmessage may be sequentially presented to a user in a tactile form in asame context according to a corresponding password rule.

It should be noted that the time sequence mentioned above may beunderstood as a sequence of events related to the notification message.For example, a package is first collected, then transferred, and finallysigned for. For example, for a flight, a ticket is first issued, thenpassages board a plane, and finally the plane takes off. The timesequence may alternatively be understood as a time when the mobileterminal receives the notification message.

In an embodiment of the present invention, if the first notificationmessage and the second notification message are presented in a visualeffect form, a first interface element is configured in the interfacepresenting the first notification message and the second notificationmessage. The method further includes: obtaining an instruction fortriggering the first interface element by the user, and invoking a thirdapplication. A semantic feature value of the third application matchesthe semantic feature value of the first notification message, or asemantic feature value of the third application matches the semanticfeature value of the second notification message. The interface elementis a component of a terminal interface, and usually includes a text, apicture, an icon, audio, a video, a widget, and the like. The interfaceelement may be understood as a command line used for quickly starting atask, for example, a link that is provided by a system and that is forquickly starting a program or opening a file or a folder. The interfaceelement usually exists in an icon form and is similar to a shortcut. Theshortcut is a common expression of a plurality of possible operationentries. The shortcut may be but is not limited to an application, aspecific function, a contact, a setting option, a notification bar, ashortcut operation bar, and the like. In this embodiment of the presentinvention, the shortcut may be a link for starting an application, forexample, a link for starting one of the following applications: WeChat,Google Search, a camera, and the like; or may be a link for starting anelement inside an application, for example, a link for starting acontact in a contact application, a link for starting an SMS message inan SMS application, or a link for enabling a function setting in asettings application. Herein, starting an element inside a program maybe understood as viewing the element inside the program, or triggeringthe element inside the program. An associated application may be quicklyopened by taping the interface element in the interface, therebyimproving efficiency of invoking the application.

FIG. 6A to FIG. 6C are a flowchart of a method for associatingnotification messages according to an embodiment of the presentinvention. An express delivery type notification message is used as anexample below for specific description. An implementation principle ofanother type of notification message is similar to this. As shown inFIG. 6A to FIG. 6C, a procedure for processing the express delivery typenotification message is as follows:

S601. A mobile terminal receives a notification message; or a mobileterminal opens an application and reads a notification message; or amobile terminal is in a call and reads a notification message in a voiceform. The notification message may be an SMS message in an SMSapplication (for example, the message is used to notify a user of whenand where to pick up a package), express delivery information (as shownin FIG. 1) in a Taobao application, voice information in a callapplication (for example, the information is used to notify a user ofwhen and where to pick up a package), or the like. For ease ofdescription, an SMS message is used as an example, and the notificationmessage is referred to as a first express delivery SMS message.

S602. The mobile terminal captures content related to the first expressdelivery SMS message, that is, the content capturing module 420 extractsthe message content from the first express delivery SMS message, andtransfers the extracted message content to the semantic analysis module430. The message content may include all words, a sender, a receivingtime, and the like of the first express delivery SMS message.

S603. The mobile terminal performs semantic analysis on the firstexpress delivery SMS message, that is, the semantic analysis module 430obtains a key field of the SMS message through analysis. The key fieldmay include at least one of the following fields: a message type (anexpress delivery type), an event (an item related to this SMS message,such as collection, delivery, or receipt), an express delivery number,an express delivery company, a logistics status, a time of receiving theSMS message, a time of the event related to the SMS message, a locationof the event related to the SMS message, and other related information.After obtaining the field through parsing, the semantic analysis module430 sends a semantic analysis result to the notification messagemanagement module 440, so that the notification message managementmodule 440 performs a subsequent operation.

S604. The notification message management module matches the firstexpress delivery SMS message and an existing notification message; andperforms S605 if the matching fails; or performs S606 if the matchingsucceeds. The existing notification message is a notification messagepreviously stored in the mobile terminal, and may be specifically storedin a table form based on the key field obtaining through semanticanalysis.

For a specific matching procedure, refer to S701 to S705 in FIG. 7. FIG.7 is a flowchart of notification message matching according to anembodiment of the present invention. From a perspective of softwareimplementation, the notification message matching may be executed by thenotification message management module 440. From a perspective ofhardware implementation, the processor may invoke code in the memory toperform method steps shown in FIG. 7. In S701, the notification messagemanagement module 440 obtains the key field sent by the semanticanalysis module 430, and extracts a key field of a message type. Forexample, the extracted message type is an express delivery type. InS702, the notification message management module 440 matches the expressdelivery type and a type of a notification message stored in the mobileterminal, to acknowledge whether there is a notification message whosetype is the same as or similar to the express delivery type. If thematching succeeds, the notification message management module 440performs step S703 to select an existing notification message whosemessage type is the express delivery type, and then performs S704. If avalue assigned to the message type field in the key field sent by thesemantic analysis module is null, or if a value assigned to the messagetype field is the express delivery type but the mobile terminal does notlocally store an express delivery type notification message, thenotification message management module 440 acknowledges that thematching fails, and performs step S704. In S704, the notificationmessage management module 440 extracts a key field of a notificationmessage ID. The notification message ID is used to uniquely identify thenotification message, and may be an order number of an event, forexample, an express delivery number or a flight number; or may be anidentifier that is inside the terminal and that is used to read andwrite the notification message, for example, an identifier in a binaryform. If the notification message management module 440 acknowledgesthat there is a notification message whose ID is the same as thenotification message ID, the notification message management module 440acknowledges that the matching succeeds, and performs step S706. If thenotification message module 440 does not obtain the notification messageID, that is, a value assigned to the notification message ID is null,the notification message management module 440 acknowledges that themobile terminal does not store a notification message related to theevent related to the notification message. If the notification messageis an express delivery message, it may be understood that the mobileterminal does not store a notification message related to an expressdelivery number of express delivery, and step S705 is performed. InS705, that the notification message management module 440 refreshes allnotification messages may be understood as that the notification messagemanagement module 440 stores the notification message in the memory ofthe mobile terminal. Refreshing all the notification messages herein maybe refreshing all types of notification messages stored in the mobileterminal, for example, refreshing notification messages of all typessuch as an express delivery type, a flight type, and a chat type; orrefreshing this type of notification message stored in the mobileterminal. If the notification message is an express delivery typenotification message, all notification messages of the express deliverytype are refreshed, and another type of notification message is notrefreshed.

To be specific, in step S604, a matching success may include a case inwhich the first express delivery SMS message and the existingnotification message match in terms of at least one of the two keyfields: the message type and the notification message ID. A matchingfailure may be understood in a broad sense, and may include at least twocases. First, a key field in a notification message is null, or is notassigned with a value. In this case, matching cannot be performed, andthis may be considered as a matching failure. Second, a notificationmessage includes a key field, but the key field is different from or isnot similar to a key field stored in the mobile terminal.

S605. If the matching fails, the notification message management module440 refreshes the existing notification message in the mobile terminal.For details, refer to the content described in S705.

S606. If the matching succeeds, that is, it is acknowledged that themobile terminal stores a notification message related to the firstexpress delivery SMS message, the notification message management module440 obtains an express delivery state related to the first expressdelivery SMS message, and compares the express delivery state with astored express delivery state to determine whether the express deliverystate stored in the mobile terminal needs to be updated. Thenotification message management module 440 performs S607 if the expressdelivery state needs to be updated; or ends the procedures if theexpress delivery state does not need to be updated.

For specific implementation, refer to S706 to S708 in FIG. 7. Forexample, the content of the first express delivery SMS message isdelivery information. As shown in FIG. 9, the content of the SMS messageis “[STO.Express] Your STO package 12045687464564 has arrived at thesouth gate of your residential district. Please pick it up before11:00”. A sending phone number is 13546785456. A notification messagethat is stored in the mobile terminal and that is related to the expressdelivery is shown in FIG. 8, and includes collection information,transit information, delivery information, and the like. In S706, thenotification message management module 440 obtains the notificationmessage that is stored in the mobile terminal and that is related to theexpress delivery. In S707, the notification message management module440 obtains a key field of an event status of the first express deliverySMS message, and compares the event status with an event status that isstored in the terminal and that is related to the express delivery. Thenotification message management module 440 performs step S705 if thefield is null in the notification message, that is, the notificationmessage does not include status information of the express delivery, orthe event status field in the notification message shows that an eventstatus of the notification message is a state stored in the mobileterminal. The notification message management module 440 performs stepS708 if the event status field of the notification message actuallyshows that an event status of the notification message is a state thatis not stored in the mobile terminal and is a new state. Specifically,the event status of the first express delivery SMS message shows that anexpress delivery status is a pickup notification, and is in a state inwhich a user is instructed to pick up a package. The notificationmessage management module 440 compares the pickup notification with thecollection information, the transit information, the deliveryinformation, and the like shown in FIG. 8, and determines that thepickup notification state does not match the state stored in the mobileterminal. In this case, the notification message management module 440determines that the notification message of the express delivery needsto be updated, and performs step S708 to update a status of the expressdelivery event. To be specific, in an embodiment of the presentinvention, the first notification message is used to indicate that theevent is in a first state, and the second notification message is usedto indicate that the event is in a second state. Before the firstnotification message in the first application is obtained in S501, themethod further includes: storing a status of the event as the secondstate. After the first notification message in the first application isobtained in S501, for example, after S504, the method further includes:updating a current status of the event to the first state. Further, ifthe first state is an important state in a life cycle of the event, forexample, a collected state, a state of being transferred, or a state ofbeing delivered of the package, after the updating a status of the eventto the first state, the method further includes: notifying the user thatthe current status of the event is the first state, for example,notifying the user that the current status of the package is “beingdelivered”. There are various reminding manners, for example,conventional optical, acoustic, and electrical forms, or highlighteddisplay in an interface, or prompt information presented in anotification bar. This is not limited.

S607. After determining that the status of the event related to thenotification message needs to be updated, the notification messagemanagement module 440 updates the status, to update the express deliverystatus to a state related to the first express delivery SMS message. Theupdate may be storing only the first express delivery SMS message, or asshown in FIG. 10, may be presenting the content of the first expressdelivery SMS message together with content that is stored in the mobileterminal in addition to storing the first express delivery SMS message.

Adaptively, if the user fails to pick up the package in a timely mannerdue to a delay caused by a matter, a courier places the package in anintelligent self-express service machine, and sends a location and apassword of the intelligent self-express service machine to the user byusing an SMS message, as shown in FIG. 11. The content capturing module420, the semantic analysis module 430, and the notification messagemanagement module 440 perform the foregoing method procedure again, thatis, S601 to S607 shown in FIG. 6A and FIG. 6B, to gather the storedcontent and the content mentioned in the SMS message such as thelocation and the password of the intelligent self-express servicemachine, and finally present an interface shown in FIG. 12. That is, theSMS message is associated with the previously stored content related tothe express delivery, to present the SMS message and the content in asame interface.

S608. After updating the express delivery status, the notificationmessage management module 440 may further determine whether the pickupnotification is an important state of the express delivery event, thatis, determine whether the updated state is an important state of theevent; and perform S609 if the updated state is related to importantstatus information; or end the procedure if the updated state is notrelated to important status information.

An important state is a state that plays a key role in development of anevent in a whole procedure of the entire event. For example,“collected”. “being transferred”, “being delivered”, “signed”, and thelike in an express delivery context, booking, boarding, departure,landing, and the like in a flight context; ordering, car pickup,payment, car return, and the like in a car rental context; ordering,payment, use, and the like in a context of purchasing a movie ticketonline; or a handling transaction, a handling time, a handling location,a related amount, and the like in a bank reminding context. Theimportant state may be customized by a user, may be determined by themobile terminal based on semantic analysis, may be generated by theterminal through a plurality times of learning, or may be pushed by aserver to the mobile terminal after analyzing a large amount of data. Inthis embodiment, the pickup notification is an important item in adelivery phase. If a user is not notified of when and where to pick up apackage, the express delivery may be unable to be completed finally.Therefore, the pickup notification is related to the important statusinformation, and S609 is performed.

S609. After determining that the updated state is the important state ofthe event, the notification message management module 440 reminds theuser that the status of the event is updated, that is, reminds the userthat the express delivery status is updated, and asks the user to viewthe express delivery status in a timely manner. A specific remindingmanner is not limited, and may be at least one of reminders such as asound, light, or vibration. Alternatively, the user may be reminded byusing a wearable device such as a band or a watch. Alternatively, in aspecific environment, a possible peripheral facility may be used toremind the user. For example, in an in-vehicle environment, an animationmay be played on a display screen used in a vehicle.

In the foregoing embodiment of the present invention, S604-S610 in FIG.6B and FIG. 6C are performed by the notification message managementmodule 440, and S701-S11 in FIG. 7 are performed by the notificationmessage management module 440.

In another embodiment of the present invention, the methods shown inFIG. 5, FIG. 6A to FIG. 6C, and FIG. 7 may alternatively be applied toanother type of notification message. A flight type notification messageand an online shopping type notification message are used as an examplebelow for brief description. For description of a same or correspondingmethod procedure, refer to the description for the express delivery typenotification message.

FIG. 13, FIG. 14, FIG. 15, FIG. 16, FIG. 17, and FIG. 18 are schematicdisplay diagrams of a flight type notification message according to anembodiment of the present invention. As shown in FIG. 13, a user wantsto book a flight ticket from Beijing to Shanghai. The user does notselect a specific airline or limit a price range, and taps a “search”key to search for the flight ticket. It is assumed that the user findsflight information shown in FIG. 14, and determines a flight number, aflight time, a name of passenger, a price, and the like. In this case,the user is in a stage of acknowledging an order without paying for theorder. The user taps a “precede to payment” key shown in FIG. 14, andafter the payment is completed, an order details page shown in FIG. 15is presented. An order status indicates that a current status is a stagein which the ticket is purchased but is not issued. After issuing theticket, the airline sends an SMS message shown in FIG. 16 to the user.The SMS message is used to notify the user that the ticket is issued,and ask the user to check passage and flight information. In an entireprocess, a plurality of interfaces in FIG. 13 to FIG. 16 appear. Almostall the interfaces include notification information, and each piece ofnotification information includes corresponding content. By performingthe method provided in this embodiment of the present invention, themobile terminal may finally present an interface shown in FIG. 17, toinform the user of progress of the flight type notification message. Itshould be understood that FIG. 17 presents complete information relatedto the flight. Certainly, some notification messages may be presentedalong with progress in booking the flight ticket. For example, only alowest notification message may be presented in a state in which thepayment is completed but no SMS message for acknowledgement is received.

FIG. 17 shows an interface in which key fields are finally presentedbased on a time sequence after the mobile terminal performs semanticanalysis on notification messages shown in FIG. 13 to FIG. 16 to extractthe key fields from the notification messages, and arranges the keyfields according to a specific rule. For ease of description. 1, 2, and3 are used for marking the foregoing notification messages. A messagerecord numbered 1 is information presented after the mobile terminalperforms semantic analysis on notification messages shown in FIG. 13 toFIG. 15 to capture key fields. A message record numbered 2 isinformation presented after the mobile terminal performs semanticanalysis on the SMS message shown in FIG. 16 to capture a key field. Amessage record numbered 3 is schedule reminders automatically generatedby the mobile terminal for some items with a deadline after the mobileterminal performs semantic analysis on the items. To be specific, afterperforming semantic analysis on “check-in ends 45 minutes beforedeparture” mentioned in the SMS message shown in FIG. 16, the mobileterminal generates a reminder item one hour before departure, to remindthe user to check in as soon as possible. To be specific, in anembodiment of the present invention, the first notification message maycarry a first time point and information about an action to occur at thefirst time point, and the first time point is a future time point. Themethod described in FIG. 5 may further include: obtaining the first timepoint carried in the first notification message, and automaticallygenerating a schedule reminder based on the first time point and theinformation about the action to occur at the first time point. Theschedule reminder is used to remind, before the first time point, theuser of the action to occur at the first time point. Specifically, inthis embodiment, the first time point (45 minutes before 18:00 on August15) is carried in FIG. 16, and the action information is boarding. Afterobtaining the SMS message, the mobile terminal automatically generates areminder item based on content in the SMS message. The reminder item isused to remind the user to complete boarding before 17:15 on August 15.A reminding time may be two or three hours before departure, or may beset by the user.

Further, as shown in FIG. 18, a message record numbered 4 in FIG. 18further records airport pickup information booked by the user. Theairport pickup information may be information captured by the mobileterminal when the user subscribes to website interfaces shown in FIG. 13to FIG. 15, or may be information captured by the processor when aserver sends an SMS message to the mobile terminal after the user placesan order, or may be information captured by the processor when the userplaces an order in third-party online ride-hailing software (forexample, Uber). To be specific, the mobile terminal may further displayassociated notification messages in a same interface through semanticanalysis on, for example, scheduling of the user. In this way,efficiency of operating obtained information by the user is improved,thereby facilitating use by the user, and greatly improving userexperience. In addition, the mobile terminal may further list maininformation on a higher part of the interface, for example, present, inthe display interface, several main words “2016-08-15, departure fromShenzhen for a business trip to Beijing”, so as to help the user quicklylearn of a subject related to the message record in the interface.

FIG. 19, FIG. 20, and FIG. 21 are schematic display diagrams of anonline shopping type notification message according to an embodiment ofthe present invention. Purchasing a movie ticket online is used as anexample of online shopping. After an order for the movie ticket isplaced and payment is completed successfully, a UI shown in FIG. 19 ispresented. The interface records information such as a movie name, atheater, a seat number, a mobile phone number, and a two-dimensionalcode for ticket pickup. After the payment is completed and the theatersuccessfully issues the ticket, the server sends an SMS message shown inFIG. 20 to the mobile terminal, to inform a user of an order number, thetheater, a ticket pickup number, a theater address, and the like. Aftercapturing notification messages in FIG. 19 and FIG. 20, the mobileterminal generates a UI interface diagram shown in FIG. 21 by performingthe method in FIG. 5 or FIG. 6A to FIG. 6C.

FIG. 21 shows an interface in which key fields are finally presentedbased on a time sequence after the mobile terminal performs semanticanalysis on the notification messages shown in FIG. 19 and FIG. 20 toextract the key fields from the notification messages, and arranges thekey fields according to a specific rule. A lowest message record isinformation presented after the mobile terminal performs semanticanalysis on a notification message shown in FIG. 19 to capture a keyfield. A middle message record is information presented after the mobileterminal performs semantic analysis on an SMS message shown in FIG. 20to capture a key field. A highest message record is schedule remindersautomatically generated by the mobile terminal for some items with adeadline after performing semantic analysis on the items. To bespecific, after performing semantic analysis on “18:00-20:00” shown inFIG. 19 or FIG. 20, the mobile terminal generates a reminder item halfan hour before a movie starts, to remind the user to watch the movie.Further, as shown in FIG. 21, shortcuts of “one-tap navigation” and“one-tap ticket pickup” are further provided in the highest messagerecord in the UI interface. The user taps the shortcut of “one-tapnavigation”, and the mobile terminal automatically runs map software toperform a navigation operation by using “No. 16 Houhai Avenue, NanshanDistrict, Shenzhen” mentioned in the SMS message in FIG. 20 as adestination. The user taps the shortcut of “one-tap ticket pickup”, andthe mobile terminal automatically displays the two-dimensional code forticket pickup in the message in FIG. 19 on a full screen, so that theuser scans the two-dimensional code for ticket pickup and brushes theticket. Alternatively, the mobile terminal and a ticket pickup machineare in a proximity connection, for example, a Bluetooth connection or anNFC connection. After the user taps the “one-tap ticket pickup”, themobile terminal invokes the Bluetooth connection or the NFC connectionto send a packet to the ticket pickup machine. The packet carriesinformation about the two-dimensional code for ticket pickup orinformation about the ticket pickup number. After obtaining the packet,the ticket pickup machine verifies whether the packet is valid, andprints the movie ticket after the verification succeeds. By providingthe shortcut, the user conveniently invokes an application or a processassociated with an event of the notification message, thereby reducing aquantity of operations performed by the user, and effectively improvingoperation efficiency of the user. Likewise, the mobile terminal mayfurther list main information on a higher part of the interface, forexample, present, in the display interface, several main words“2016-08-12, to watch a movie in Taikoo Shing”, so as to help the userquickly learn of a subject related to the message record in theinterface.

In an optional implementation, the first notification message carries afirst location and information about an action to occur at the firstlocation. The method described in FIG. 5 may further include: obtaininga current location of the mobile terminal, and automatically generatinga reminder item if deviation between the current location of the mobileterminal and the first location falls within a preset deviation range.The reminder item is used to prompt for the information about the actionto occur at the first location. Specifically, in this embodiment, theSMS message shown in FIG. 20 carries the first location (No. 16 HouhaiAvenue, Nanshan District, Shenzhen) and the action information (watchinga movie). When a mobile phone carried by the user records real-timegeographic location information of the user, and a real-time geographiclocation of the user is near the first location, the mobile phonegenerates a reminder item to remind the user to watch the movie near thelocation. Further, a location-based reminder item may be combined with atime-based reminder item. To be specific, the time-based reminder itemmay also be used to remind a location of an action to occur, and thelocation-based reminder item may also be used to remind a time when theaction to occur.

FIG. 22 is a schematic structural diagram of a mobile terminal accordingto an embodiment. For the mobile terminal, refer to the structure of themobile terminal shown in FIG. 3. The mobile terminal may be configuredto perform the methods shown in FIG. 5, FIG. 6A to FIG. 6C, and FIG. 7.For a same or corresponding technical feature, reference may be mademutually. Specifically, the mobile terminal includes one or moreprocessors 2202 and a memory 2201. The processor 2201 is connected tothe memory 2202. The memory 2201 is configured to store one or moreapplications. The processor 2202 runs the one or more applications to:obtain a first notification message in a first application; obtain asemantic feature value of the first notification message, where thesemantic feature value is used to indicate a semantic feature of thefirst notification message; determine a second notification message in asecond application, wherein a semantic feature value of the secondnotification message matches the semantic feature value of the firstnotification message, where the second notification message ispre-stored in the mobile terminal; and associate the first notificationmessage with the second notification message.

In an embodiment of the present invention, that the processor determinesthat a semantic feature value of a second notification message matchesthe semantic feature value of the first notification message isspecifically as follows: The processor determines that an event relatedto the second notification message and an event related to the firstnotification message are a same event. Further, the first notificationmessage is used to indicate that the event is in a first state, and thesecond notification message is used to indicate that the event is in asecond state. The memory is further configured to store a status of theevent as the second state before the first notification message in thefirst application is obtained. The processor is further configured toupdate a current status of the event to the first state after obtainingthe first notification message in the first application. Further, if thefirst state is an important state in a life cycle of the event, theprocessor is further configured to: after updating the status of theevent to the first state, notify a user that the current status of theevent is the first state. In the foregoing implementation, the mobileterminal further includes an output device. That the processorassociates the first notification message with the second notificationmessage is specifically as follows: The processor instructs the outputdevice to sequentially present the first notification message and thesecond notification message in a same interface according to a progresssequence of the event.

In an embodiment of the present invention, the processor is furtherconfigured to obtain the semantic feature value of the secondnotification message. That the processor determines that a semanticfeature value of a second notification message matches the semanticfeature value of the first notification message is specifically asfollows: The processor determines that the semantic feature value of thesecond notification message is the same as or similar to the semanticfeature value of the first notification message.

In the foregoing embodiment of the present invention, the mobileterminal further includes an output device. That the processorassociates the first notification message with the second notificationmessage is specifically as follows: The processor instructs the outputdevice to present the first notification message and the secondnotification message in a same interface; or the processor instructs theoutput device to sequentially present the first notification message andthe second notification message in a same interface based on a timesequence of receiving the notification messages, or the processorinstructs the output device to sequentially broadcast the firstnotification message and the second notification message through a voicebased on a time sequence.

In an implementation of this embodiment of the present invention, afirst interface element is configured in the interface presenting thefirst notification message and the second notification message. Themobile terminal further includes an input device. The input device isconfigured to obtain an instruction for triggering the first interfaceelement by the user. The processor is further configured to run a thirdapplication according to the instruction that is for triggering thefirst interface element and that is obtained by the input device. Asemantic feature value of the third application matches the semanticfeature value of the first notification message, or a semantic featurevalue of the third application matches the semantic feature value of thesecond notification message.

In an implementation of this embodiment of the present invention, theoutput device presents the first notification message and the secondnotification message in an interface in the first application; or theoutput device presents the first notification message and the secondnotification message in an interface in the second application: or theprocessor regenerates an interface, and the output device presents thefirst notification message and the second notification message in theregenerated interface.

In the foregoing embodiment of the present invention, the firstnotification message carries a first time point and information about anaction to occur at the first time point, and the first time point is afuture time point. The processor is further configured to: obtain thefirst time point carried in the first notification message, andautomatically generate a schedule reminder based on the first time pointand the information about the action to occur at the first time point.The schedule reminder is used to remind, before the first time point,the user of the action to occur at the first time point. Alternatively,the first notification message carries a first location and informationabout an action to occur at the first location. The processor is furtherconfigured to: obtain a current location of the mobile terminal, andautomatically generate a reminder item if deviation between the currentlocation of the mobile terminal and the first location falls within apreset deviation range. The reminder item is used to prompt for theinformation about the action to occur at the first location.

FIG. 23 is a schematic structural diagram of an apparatus forassociating notification messages according to an embodiment. Theapparatus for associating notification messages may be a part of thestructure of the mobile terminal shown in FIG. 3 or FIG. 22, or may bean independent mobile terminal, as shown in FIG. 4. The apparatus forassociating notification messages may be configured to perform themethods shown in FIG. 5, FIG. 6A to FIG. 6C, and FIG. 7. For a same orcorresponding technical feature, reference may be made mutually.Specifically, the apparatus includes one or more first obtaining modules2301, a second obtaining module 2302, a determining module 2303, and anassociation module 2304. The first obtaining module 2301 is connected tothe second obtaining module 2302, the second obtaining module 2302 isconnected to the determining module 2303, and the association module2304 is connected to the determining module 2303. The first obtainingmodule 2301 is configured to obtain a first notification message in afirst application. The second obtaining module 2302 is configured toobtain a semantic feature value of the first notification message, wherethe semantic feature value is used to indicate a semantic feature of thefirst notification message. The determining module 2303 is configured todetermine a second notification message in a second application, whereina semantic feature value of the second notification message matches thesemantic feature value of the first notification message, where thesecond notification message is pre-stored in the mobile terminal. Theassociation module 2304 is configured to associate the firstnotification message with the second notification message.

In an embodiment of the present invention, that the determining moduledetermines that a semantic feature value of a second notificationmessage matches the semantic feature value of the first notificationmessage is specifically as follows: The determining module determinesthat an event related to the second notification message and an eventrelated to the first notification message are a same event. Further, thefirst notification message is used to indicate that the event is in afirst state, and the second notification message is used to indicatethat the event is in a second state. The apparatus further includes: astorage module, configured to store a status of the event as the secondstate before the first obtaining module obtains the first notificationmessage in the first application; and an updating module, configured toupdate a current status of the event to the first state after the firstobtaining module obtains the first notification message in the firstapplication. Further, the apparatus includes a prompt module. The promptmodule is configured to: after the updating module updates the currentstatus of the event to the first state, notify a user that the currentstatus of the event is the first state. In the foregoing implementation,the association module may be specifically configured to sequentiallypresent the first notification message and the second notificationmessage in a same interface based on a progress sequence of the event.

In an embodiment of the present invention, the apparatus furtherincludes a third obtaining module. The third obtaining module isconfigured to obtain the semantic feature value of the secondnotification message. That the determining module determines that asemantic feature value of a second notification message matches thesemantic feature value of the first notification message is specificallyas follows: The determining module determines that the semantic featurevalue of the second notification message is the same as or similar tothe semantic feature value of the first notification message.

In the foregoing embodiment of the present invention, the associationmodule is specifically configured to: present the first notificationmessage and the second notification message in a same interface; orsequentially present the first notification message and the secondnotification message in a same interface based on a time sequence ofreceiving the notification messages; or sequentially broadcast the firstnotification message and the second notification message through a voicebased on a time sequence.

In an embodiment of the present invention, a first interface element isconfigured in the interface presenting the first notification messageand the second notification message. The apparatus further includes afourth obtaining module and an invoking module. The fourth obtainingmodule is configured to obtain an instruction for triggering the firstinterface element by the user. The invoking module is configured to runa third application according to the instruction obtained by the fourthobtaining module. A semantic feature value of the third applicationmatches the semantic feature value of the first notification message, ora semantic feature value of the third application matches the semanticfeature value of the second notification message.

In an embodiment of the present invention, the interface presenting thefirst notification message and the second notification message is aninterface in the first application; or the interface presenting thefirst notification message and the second notification message is aninterface in the second application; or the interface presenting thefirst notification message and the second notification message is aninterface regenerated by the mobile terminal.

In the foregoing embodiment of the present invention, the firstnotification message carries a first time point and information about anaction to occur at the first time point, and the first time point is afuture time point. The apparatus further includes: a fifth obtainingmodule, configured to obtain the first time point carried in the firstnotification message; and a first generation module, configured toautomatically generate a schedule reminder based on the first time pointand the information about the action to occur at the first time point.The schedule reminder is used to remind, before the first time point,the user of the action to occur at the first time point. Alternatively,the first notification message carries a first location and informationabout an action to occur at the first location. The apparatus includes:a sixth obtaining module, configured to obtain a current location of themobile terminal; and a second generation module, configured toautomatically generate a reminder item if deviation between the currentlocation of the mobile terminal and the first location falls within apreset deviation range. The reminder item is used to prompt for theinformation about the action to occur at the first location.

An embodiment of the present invention further provides a computerreadable storage medium storing one or more programs. The one or moreprograms include an instruction, and when the instruction is executed bya mobile terminal including a plurality of applications, the mobileterminal is enabled to perform the method in the embodiment shown in anyone of FIG. 5, FIG. 6A to FIG. 6C, and FIG. 7.

It should be noted that in the embodiments of the present invention,descriptions such as “first” and “second” are only used to distinguishbetween described objects, and do not have actual meanings. A portableelectronic device is equivalent to a mobile terminal.

Function modules in the embodiments of the present invention may beintegrated into one processing unit/module, or each of the modules mayexist alone physically, or two or more modules may be integrated intoone module. The integrated module may be implemented in a form ofhardware, or may be implemented in a form of hardware in addition to asoftware function unit.

It may be clearly understood by persons skilled in the art that for thepurpose of convenient and brief description, division of the foregoingfunction modules is taken as an example for illustration. In actualapplication, the foregoing functions can be allocated to differentfunction modules and implemented according to a requirement, that is, aninner structure of an apparatus is divided into different functionmodules to implement all or some of the functions described above. For adetailed working process of the apparatus, refer to a correspondingprocess in the method embodiments. An implementation principle and atechnical effect of the apparatus are similar to those of the methodembodiments, and a same or corresponding technical feature is notdescribed herein again.

Finally, it should be noted that the foregoing embodiments are merelyintended for describing the technical solutions of the presentinvention, but not for limiting the present invention. Although thepresent invention is described in detail with reference to the foregoingembodiments, persons of ordinary skill in the art should understand thatthey may still make modifications to the technical solutions describedin the foregoing embodiments or make equivalent replacements to some orall technical features thereof, without departing from the scope of thetechnical solutions of the embodiments of the present invention.

What is claimed is:
 1. A method for associating notification messages,wherein the method is applied to a mobile terminal, and wherein themethod comprises: obtaining a first notification message in a firstapplication; obtaining a semantic feature value of the firstnotification message, wherein the semantic feature value indicates asemantic feature of the first notification message; determining a secondnotification message in a second application, wherein a semantic featurevalue of the second notification message matches the semantic featurevalue of the first notification message, wherein the second notificationmessage is pre-stored in the mobile terminal, and wherein the semanticfeature value of the second notification message is matched with thesemantic feature value of the first notification message by identifyingthat an event related to the second notification message and an eventrelated the first notification message are a same event; associating thefirst notification message with the second notification message, whereinthe first notification message indicates that the event is in a firststate, and wherein the second notification message indicates that theevent is in a second state; storing a status of the event as the secondstate before obtaining the first notification message; and updating acurrent status of the event to the first state after obtaining the firstnotification message.
 2. The method of claim 1, wherein the first stateis an important state in a life cycle of the event, and wherein themethod further comprises notifying a user that the current status of theevent is the first state after updating the current status of the eventto the first state.
 3. The method of claim 1, wherein associating thefirst notification message with the second notification messagecomprises sequentially presenting the first notification message and thesecond notification message in a same interface based on a progresssequence of the event.
 4. The method of claim 3, wherein a firstinterface element is configured in the same interface presenting thefirst notification message and the second notification message, andwherein the method further comprises: obtaining an instruction fortriggering the first interface element by a user; and invoking a thirdapplication, wherein a semantic feature value of the third applicationmatches the semantic feature value of the first notification message orthe semantic feature value of the second notification message.
 5. Themethod of claim 1, further comprising obtaining the semantic featurevalue of the second notification message, wherein a manner of matchingthe semantic feature value of the second notification message with thesemantic feature value of the first notification message comprisesidentifying that the semantic feature value of the second notificationmessage is the same as or similar to the semantic feature value of thefirst notification message.
 6. The method of claim 1, whereinassociating the first notification message with the second notificationmessage comprises any one of: presenting the first notification messageand the second notification message in a same interface; sequentiallypresenting the first notification message and the second notificationmessage in the same interface based on a time sequence of receivingnotification messages; or sequentially broadcasting the firstnotification message and the second notification message through a voicebased on a time sequence.
 7. A mobile terminal, comprising: a memoryconfigured to store at least one application; and at least one processorcoupled to the memory, wherein the at least one application causes theat least one processor to be configured to: obtain a first notificationmessage in a first application; obtain a semantic feature value of thefirst notification message, wherein the semantic feature value indicatesa semantic feature of the first notification message; determine a secondnotification message in a second application, wherein a semantic featurevalue of the second notification message matches the semantic featurevalue of the first notification message, wherein the second notificationmessage is pre-stored in the mobile terminal, and wherein in determiningthat the semantic feature value of the second notification messagematches the semantic feature value of the first notification message,the at least one application further causes the at least one processorto be configured to determine that an event related to the secondnotification message and an event related to the first notificationmessage are a same event; and associate the first notification messagewith the second notification message, wherein the first notificationmessage indicates that the event is in a first state, wherein the secondnotification message indicates that the event is in a second state,wherein the memory is further configured to store a status of the eventas the second state before obtaining the first notification message inthe first application, and wherein the at least one application furthercauses the at least one processor to be configured to update a currentstatus of the event to the first state after obtaining the firstnotification message in the first application.
 8. The mobile terminal ofclaim 7, wherein the first state is an important state in a life cycleof the event, and wherein the at least one application further causesthe at least one processor to be configured to notify a user that thecurrent status of the event is the first state after updating thecurrent status of the event to the first state.
 9. The mobile terminalof claim 7, wherein the at least one application further causes the atleast one processor to be configured to obtain the semantic featurevalue of the second notification message, and wherein in a manner ofdetermining that the semantic feature value of the second notificationmessage matches the semantic feature value of the first notificationmessage, the at least one application further causes the at least oneprocessor to be configured to determine that the semantic feature valueof the second notification message is the same as or similar to thesemantic feature value of the first notification message.
 10. The mobileterminal of claim 7, further comprising an output device coupled to theat least one processor, and wherein in a manner of associating the firstnotification message with the second notification message, the at leastone application further causes the at least one processor to beconfigured to instruct the output device to sequentially present thefirst notification message and the second notification message in a sameinterface based on a progress sequence of an event.
 11. The mobileterminal of claim 10, wherein a first interface element is configured inthe same interface presenting the first notification message and thesecond notification message, wherein the mobile terminal furthercomprises an input device coupled to the at least one processor andconfigured to obtain an instruction for triggering the first interfaceelement by a user, wherein the at least one application further causesthe at least one processor to be configured to invoke a thirdapplication according to the instruction for triggering the firstinterface element, and wherein a semantic feature value of the thirdapplication matches the semantic feature value of the first notificationmessage or the semantic feature value of the second notificationmessage.
 12. The mobile terminal of claim 10, wherein the output deviceis further configured to: present the first notification message and thesecond notification message in an interface in the first application;present the first notification message and the second notificationmessage in an interface in the second application; or present the firstnotification message and the second notification message in aregenerated interface that is regenerated by the processor.
 13. Themobile terminal of claim 7, further comprising an output device coupledto the at least one processor, and wherein in a manner of associatingthe first notification message with the second notification message, theat least one application further causes the at least one processor to beconfigured to perform any one of: instruct the output device to presentthe first notification message and the second notification message in asame interface; instruct the output device to present the firstnotification message and the second notification message in the sameinterface based on a time sequence of receiving notification messages;or instruct the output device to sequentially broadcast the firstnotification message and the second notification message through a voicebased on a time sequence.
 14. The mobile terminal of claim 7, whereinthe first notification message carries a first time point andinformation about an action to occur at the first time point, whereinthe first time point is a future time point, and wherein the at leastone application further causes the at least one processor to beconfigured to: obtain the first time point carried in the firstnotification message; and generate a schedule reminder based on thefirst time point and the information about the action to occur at thefirst time point, wherein the schedule reminder reminds, before thefirst time point, a user of the action to occur at the first time point.15. The mobile terminal of claim 7, wherein the first notificationmessage carries a first location and information about an action tooccur at the first location, and wherein the at least one applicationfurther causes the at least one processor to be configured to: obtain acurrent location of the mobile terminal; and generate a reminder itemwhen deviation between the current location of the mobile terminal andthe first location falls within a preset deviation range, wherein thereminder item prompts for the information about the action to occur atthe first location.
 16. The mobile terminal of claim 7, wherein thesemantic feature value of the first notification message comprises atleast one of: a type of an event; a status of the event; a time relatedto the event; a location related to the event; an order number relatedto the event; a person related to the event; a time when the mobileterminal receives the first notification message; or a sender of thefirst notification message.
 17. A mobile terminal, comprising: a memoryconfigured to store at least one application; and at least one processorcoupled to the memory, wherein the at least one application causes theat least one processor to be configured to: obtain a first notificationmessage in a first application; obtain a semantic feature value of thefirst notification message, wherein the semantic feature value indicatesa semantic feature of the first notification message; determine a secondnotification message in a second application, wherein a semantic featurevalue of the second notification message matches the semantic featurevalue of the first notification message, and wherein the secondnotification message is pre-stored in the mobile terminal; associate thefirst notification message with the second notification message, whereinthe first notification message carries a first time point andinformation about an action to occur at the first time point, andwherein the first time point is a future time point; obtain the firsttime point carried in the first notification message; and generate aschedule reminder based on the first time point and the informationabout the action to occur at the first time point, wherein the schedulereminder reminds, before the first time point, a user of the action tooccur at the first time point.
 18. The mobile terminal of claim 17,wherein the semantic feature value of the first notification messagecomprises a type of an event.
 19. The mobile terminal of claim 17,wherein the semantic feature value of the first notification messagecomprises a person related to an event.
 20. The mobile terminal of claim17, wherein the semantic feature value of the first notification messagecomprises a sender of the first notification message.